build: fix docs site styling token loading #30884
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Looks like due to some rebasing, the incorrect target was used, so that the token assets wasn't available.
devversion
requested review from
adolgachev and
wagnermaciel
and removed request for
a team
devversion
added
the
target: patch
angular-robot
bot
added
the
area: build & ci
andrewseguin
approved these changes
Apr 16, 2025
devversion
added a commit
that referenced
this pull request
Apr 16, 2025
Looks like due to some rebasing, the incorrect target was used, so that the token assets wasn't available. (cherry picked from commit 2a2ab94)
|
The changes were merged into the following branches: main, 19.2.x |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Looks like due to some rebasing, the incorrect target was used, so that the token assets wasn't available.